Skip to content

feat: support Rust and Tauri in core workflows - #85

Merged
jdylanmc merged 7 commits into
mainfrom
jdylanmc/rust-tauri-support
Sep 30, 2026
Merged

jdylanmc merged 7 commits into
mainfrom
jdylanmc/rust-tauri-support

Conversation

@jdylanmc

@jdylanmc jdylanmc commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Scope

Promote the reusable Rust/Tauri spike into supported, opt-in Topocode workflows.
The branded empty Home and shared catalogue from #84 remain the entry point.
This is product functionality, not a retained experiment or a consumer-local
adapter. No PR-Sniper source, authored diagrams, evidence, caches or screenshots
are included.

Portions of the parser and conservative bridge implementation originate from
the retained experiment in #83. The production implementation lives in packaged
first-party modules; it does not invoke the spike executable or import private
consumer files. Related roadmap: #1.

Changes

  • Add explicit first-party language/framework composition to normal scan,
    validation, preview, serving and bundle workflows. JavaScript/TypeScript
    remains the default; Rust and Tauri are opt-in.
  • Preserve deterministic lexical identities and conservative invocation joins,
    including shadowing, mutation, shared-value/site-identity and ownership
    regressions. Display partial coverage and unresolved observations.
  • Add snapshot-bound technical Workflow stories, Rust anchors, exact node/edge
    evidence, and explicit source-traced versus inferred connections.
  • Add an explicit Graphviz branch-capable backend with its own validation and
    provenance. Retain the five native Archify families without modifying the
    pristine renderer package.
  • Make Home, evidence, authored/generated viewers and default exports follow
    one application theme, including focus navigation and native theme controls.
  • Stage complete generated output, roll back reported replacement failures,
    preserve renderer-owned assets and validate final shared runtime hashes.
  • Ship generic fixtures, installed skills, reconstruction instructions, all
    transferable spike findings, and consolidated changelog entries.

License decision

The owner explicitly authorized the narrow embedded Graphviz 16.0.0 EPL-2.0
exception in @viz-js/[email protected]. The implementation pins component, backend,
build-source and material provenance, retains complete notices and source
availability, and tests attribution drift. EPL-2.0 is not added to the global
allowlist; the wrapper's MIT license is not represented as covering its engine.

Acceptance and evidence

Candidate: 6fafcb113b007c3db6949438e19deae2526c9880.

Area Current evidence
Existing and composed workflows Local lint, typecheck, build, full root/workspace tests (including 75 language tests) and license checks pass
Browser integration 58/58 local browser tests pass, including native families and technical stories
Real distribution Same packed candidate passes clean installs and workflows on Node 22 and 24
Fresh reconstruction Generic mixed fixture, fresh HOME, network-forbidden operation, cache recreation, stable IDs, stale-source rejection/repair, real serve and bundle
Optional runtime Actual omitted-optional install preserves JS/TS operation and reports explicit Rust unavailability
Independent consumer Delivery owner independently repeated the final method-bearing packed consumer successfully; the same fixed package also passes on Node 22 and 24
Independent whole-change review Complete at 2ea491b; all five findings independently verified addressed at 6fafcb1, no new significant findings; 90 focused tests, two browser journeys and independent CLI probes pass
Hosted Linux CI Run 36791422193 passed at final head 6fafcb113b007c3db6949438e19deae2526c9880

Limits

  • Rust/Tauri evidence is parser-backed and deliberately partial. No compiler
    control-flow graph, complete name resolution, macro expansion, Cargo execution
    or runtime reachability is claimed.
  • Rust/Tauri scans require --allow-partial; published partial previews retain
    the documented exit code 2 rather than claiming complete analysis.
  • Graphviz provides SVG export and its documented structural/layout checks,
    not native motion/raster features or universal spline/label clearance.
  • Generation rollback covers reported errors, not filesystem crash atomicity.
  • Generic fixtures and automated checks do not establish human semantic
    approval, large-repository performance or unexecuted platform guarantees.
  • No npm publication/version release or monitoring schedule is included.

The owner requested normal landing on main after independent review and
current-head checks. Both are now complete for the candidate above, based on
current main at 4b8c085684c34384d18b27079e233838e1bc3b8c. Normal provider
merge gates still apply; no approval vote, auto-merge or protection bypass is used.

Independently verified review fixes

The first complete review identified Rust method kind readback, uncertain
spread/rest propagation, computed-property mutation invalidation, line-sensitive
impl/method identity, and Windows checkout conversion of byte-pinned notices.
The same implementation owner corrected these with method-bearing normal-command
journeys, runtime-controlled binding tests, structural owner identity tests and
actual Windows-style checkout filters. All six pinned license files retain their
exact digests. The independent reviewer replayed the counterexamples, verified
all five fixes, found no new significant issue and carried forward the original
whole-deliverable coverage. Current-head hosted CI also passed.

Partial implementation only; not a delivery-ready candidate. Graphviz 16.0.0 embeds EPL-2.0 code, which conflicts with the current exact license policy. Stop pending parent authorization of a narrow exception or approved alternative.

Typecheck and workspace rollback tests pass. Story schema strictRequired tests and composed graph module-version validation still fail. Full browser, package, license and integration gates remain incomplete.
Complete first-party adapter composition and snapshot-bound technical\nviews through normal commands. Keep native runtime bytes pristine and\nmake app-owned themes cover navigation and default exports.\n\nAdopt only the authorized exact embedded Graphviz component, with\nbackend provenance, full attribution and source availability checks.\nPreserve portable authoring, packed-consumer and cache-rebuild evidence.
Keep exact source excerpts inside the existing single details control.
Include supported examples in the enforced lint inventory and keep the
package-map fixture aligned with the new language boundary.
Share Rust kinds with persisted Repository validation and keep named
method identities independent of owner positions. Reject uncertain
spread/rest argument propagation and overwritten computed helpers.

Keep pinned license bytes unchanged by Git checkout conversion. Extend
real consumer, browser and runtime-controlled parser regressions for
RT-1 through RT-5 without relaxing existing integrity or layout gates.
@jdylanmc
jdylanmc marked this pull request as ready for review September 30, 2026 23:44
@jdylanmc
jdylanmc merged commit 0351823 into main Sep 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant